Mapping relationships between members in a social network

ABSTRACT

A system, method, and computer program for social mapping is provided. Data about a plurality of social network members is received. A first member of the plurality of social network members is allowed to identify a second member of the plurality of social network members with whom the first member wishes to establish a relationship. The data is then sent to the second member about the first member based on the identification. Input from the second member is received in response to the data. The relationship between the first member and the second member is confirmed based on the input in order to map the first member to the second member.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 11/639,655, filed on Dec. 14, 2006, which claims the benefit and priority of U.S. provisional patent application Ser. No. 60/750,844 filed on Dec. 14, 2005 and entitled “Systems and Methods for Social Mapping,” each of which is herein incorporated by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates generally to social networking, and more particularly to systems and methods for social mapping.

Description of Related Art

Conventionally, people have networked with one another by joining social clubs, attending social events, meeting friends through other friends, and so forth. The Internet has made keeping in touch with friends and acquaintances more convenient for many people. For other people, the Internet provides a social forum for networking and meeting new people.

For many people, the Internet more recently represents the principal way in which people meet new friends and remain in touch with existing friends. Thus, the Internet provides a medium for a complex array of interactions between vast numbers of individuals.

In order to facilitate communications between the vast numbers of individuals, various social networking websites have developed in recent years. Social networking websites can provide organizational tools and forums for allowing these individuals to interact with one another via the websites. However, many users are leery about providing information via the Internet. Many users prefer to limit communications to specific groups of other users, for example.

SUMMARY OF THE INVENTION

The present invention provides a system, method, and computer program for social mapping. Data about one or more social network members is received. A first social network member is allowed to identify at least one second social network member to establish a relationship. Data about the first social network member is then sent to the second social network member based on the identification. Input from the second social network member is received in response to the data. The relationship is confirmed based on the input in order to map the first social network member to the second social network member.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic diagram of an exemplary environment for social mapping;

FIG. 2 illustrates a block diagram of an exemplary social network engine;

FIG. 3 illustrates an exemplary display page associated with the social network engine;

FIG. 4 illustrates an exemplary social editor page associated with the social network engine; and

FIG. 5 illustrates a flow diagram of an exemplary process for social mapping.

DETAILED DESCRIPTION

FIG. 1 illustrates a schematic diagram of an exemplary environment for social mapping. One or more users 102, such as a user A 102A, a user B 102B, and a user N 102N, are in communication via a network 104 with a social network engine 106. The social network engine 106 may comprise a social networking website, one or more servers operating the social networking website, or any other device or application capable of providing social networking services via the network 104. The users 102 can access the services provided by the social network engine 106 via the network 104. Optionally, one or more of the users 102 may be able to access the social network engine 106 directly.

The users 102 can access the social network engine 106 via a computing device, such as a laptop or desktop computer, a cellular telephone, a personal digital assistant (PDA), a set top box, and so forth. The users 102 can view data about social network members via the social network engine 106, enter data about themselves and possibly others, join social network groups, and so forth. The users 102 are typically members of a social networking website associated with the social network engine 106, for example, and thus comprise the social network members.

According to exemplary embodiments, a user 102, such as the user A 102A, identifies one or more other members associated with the social network engine 106, such as the user B 102B and the user N 102N, with which the user A 102A wants to build a relationship or establish or alter the details of an existing relationship. Via the social network engine 106, the user A 102A enters the details about the relationship. The social network engine 106 then sends the data, such as the data comprising the details from the user A 102A to the other users (i.e., user B 102B and user N 102N). The user B 102B and the user N 102N then provide input in response to the data. The response may, for example, modify the data.

The relationship with the user B 102B and the user N 102N is confirmed, based on the input, by the social network engine 106. The confirmation may include denying the existence of the relationship, according to some embodiments. Any type of confirmation and/or input may be utilized to alter and/or establish the relationship between the user A 102A and the user B 102B and the user N 102N.

The relationship may comprise any type of relationship that exists between two of the users 102. For example, the user A 102A and the user B 102B may have worked together, been classmates, be related, have dated, and so forth. More than one relationship may exist between the two users. For example, the user A 102A and the user B 102B may have both worked together and dated. Processing, accessing, utilizing, modifying, and so forth the relationship data between two or more users is discussed further in association with FIGS. 2 through 5.

Referring now to FIG. 2, a block diagram of an exemplary social network engine, such as the social network engine 106 discussed in FIG. 1, is illustrated. A communications interface 202 is provided in association with the social network engine 106 for receiving data from and sending data to the users 102. The users 102 can send any type of data to the social network engine 106 via the network 104 and vice versa.

Typically, the users 102 access a website associated with the social network engine 106. For example, the social network engine 106 may host a social networking website where the users 102 can visit to interact with one another. The website can display various types of data about the users 102 to one another, such as profile information, or relationships a particular user, such as the user A 102A, has with other users, such as the user B 102B and the user N 102N. The users 102 may belong to particular communities within the social networking website, such as communities categorized according to school attended, workplace, geographical location, and so forth.

A social relationship editor module 204 is provided for editing the social relationships that the users 102 have with one another. For example, the user A 102A can specify a particular relationship with the user B 102B and the user N 102N. The user B 102B and/or the user N 102N may then be asked to confirm the particular relationship specified by the user A 102A. Accordingly, each relationship established via the social networking website is verified by two or more of the users 102 in the relationship. A social relationship editor display page associated with the social relationship editor module 204 is discussed further in association with FIG. 3.

The social relationship editor module 204 can track the one or more relationships between the users 102. The social relationship editor module 204 can also generate and send communications to the users 102 to confirm the relationships identified. As discussed herein, the users 102 are typically members of the social networking website. Accordingly, the users 102 interact with one another via the social network website associated with the social network engine 106 and can identify relationships with one another in order to facilitate the interactions, or for any other reason.

A relationship storage module 206 is provided for facilitating storage of the relationships between the users 102. The relationship storage module 206 can utilize any type of storage device or medium to store the various relationships. For example, the relationship storage module 206 can store the relationships in databases, on CD ROMS, in DRAM, and so forth. Any type of storage device or storage medium for storing the relationships, profile data associated with the users 102, or any other information associated with the users 102, is within the scope of various embodiments.

A relationship display module 208 is also provided in association with the social network engine 106. The relationship display module 208 identifies the relationships between the users 102 and generates a display page that indicates profile information, relationships, and other data about the users 102. For example, the user A 102A may be able to request, via a button, portal, link, and so forth, a display page regarding people from a particular community associated with the user A 102A, such as a college community. The relationship display module 208 can then generate and display data about the users 102 belonging to the particular community associated with the user A 102A to the user A 102A. The user A 102A can then utilize the display page to access more detailed data about each of the users 102 listed on the display page. The relationship display module 208 may display any data about the users 102 associated with the social networking site.

Although FIG. 2 shows various modules associated with the social network engine 106 (e.g., the communications interface 202, the social relationship editor module 204, the relationship storage module 206, and the relationship display module 208), fewer or more modules may be associated with the social network engine 106 and still fall within the scope of various embodiments. For example, a database (not shown) may be coupled to the social network engine 106 for storing data about the users 102.

FIG. 3 illustrates an exemplary social network display page 300 that may be associated with the social network engine 106. The social network display page 300 includes a pictorial/graphical representation 302 for each of the users 102. For example, the user A 102A may utilize a photo of the user A 102, while the user B 102B may utilize a cartoon character to represent the user B 102B. Any type of picture, photo, graphic, icon, symbol, and so forth may be utilized to represent the users 102 via the pictorial/graphical representation 302.

Biographical data 304 is displayed about each of the users 102 that are listed. For example, the name, status, year of graduation, field of study, and so forth may be displayed as the biographical data 304 for each of the users 102. Any type of data may comprise the biographical data 304.

A user action area 306 may be associated with the social network display page 300. For example, the user action area 306 may be displayed in association with each of the users 102. In FIG. 3, the user action area 306 is displayed to the right of the biographical data 304 for each of the users 102. However, the user action area 306 may be displayed anywhere. For example, the pictorial/graphical representation 302 may be accessed, check-marked, highlighted, and so forth in order to display the user action area 306.

The user action area 306 allows the users 102 to select one or more actions to perform in association with a particular user, such as the user A 102A, about which the biographical data 304 is being viewed. For example, the users 102 can choose to send the users 102 an email or other message via the “send message” function, or to utilize a “poke her!” function to be directed to a pop-up or similar screen, confirming that the user 102 wishes to “poke” a displayed user. An announcement may be sent to the displayed user informing the displayed user that the displayed user has been “poked” by another user 102.

The user action area 306 may also allow the users 102 to utilize a “view friends” function” in order to view the data about friends of the users 102, to utilize a “view photos” function to view photos associated with the user, and/or an “add to friends” function to request addition to a friends group of the user 102. Various other options may be accessed via the user action area 306. For example, the users 102 may be able to access stories about a particular user, such as the user B 102B, via the user action area 306.

The social network display page 300 may be utilized for displaying any type of data about the users 102. The social network display page 300 shown in FIG. 3 is an exemplary display page for displaying various users belonging to a community. Display pages may also be utilized to display profile data about individual users or groups of users, to display data about the users 102 belonging to various communities, to display stories about the users 102, and so forth. The social network display page 300 in FIG. 3 may be utilized, according to exemplary embodiments, to identify and/or select the users 102 known to a particular user, such as the user A 102A with whom the user A 102A wants to establish a relationship. The social network display page 300 may be generated by the relationship display module 208 and be displayed in response to a search or filter function initiated by the user A 102A, such as a search performed. As discussed herein, the data about the users 102 for the social network display page 300 may be stored in a database, cache memory, or any other memory utilized by the relationship storage module 206 or another storage module (not shown) for storing data about the users 102.

According to some embodiments, the social network display page 300 may be utilized to display a directory of the users 102, a collection of the users 102, a directory of established relationships associated with the user A 102A, for example, and so forth. As discussed herein, any of the data associated with the users 102 may be displayed utilizing the social network display page 300 or any other display mechanism associated with the social network engine 106.

FIG. 4 illustrates an exemplary social editor page associated with the social network engine 106. The social editor page 400 illustrated in FIG. 4 can be utilized to question the users 102 about the relationships with other users 102 associated with the social networking website. The social editor page 400 may be sent in response to a request from a particular user, such as the user A 102A, to form or otherwise establish a relationship with another user, such as the user B 102B, for example.

A social editor inquiry 402 may be utilized to establish the subject matter for the social editor page 400. For example, FIG. 4 illustrates the social editor page 400 for the social editor inquiry 402 “How do you know John Do?” However, the social editor inquiry 402 may comprise any inquiry, such as “Is the information provided by John Do about your relationship accurate?” Any type of social editor inquiry 402 may be provided in association with the social editor page 400.

A relationship type identifier 404 may be displayed for allowing a user 102 to select and/or identify the relationship the user 102 has with other users 102. For example, the user A 102A may select that the user A 102A lived with the user B 102B, worked with the user B 102B, and/or knows the user B 102B through a friend. One or more of the relationship identifiers 404 may be selected. As discussed herein, the users 102 may know each other via more than one means.

A relationship details identifier 406 allows the users 102 to further specify the nature of the relationship. For example, the relationship details identifier 406 may establish where the users 102 lived together, where the users 102 worked together, which friends the users 102 have in common, and so forth. Although only one relationship details identifier 406 is illustrated, more than one relationship details identifier 406 associated with each of the relationships may be provided.

A timeframe identifier 408 may also be provided in association with the social editor page 400. The timeframe identifier 408 may be utilized to establish a time or timeframe associated with the relationship identifier 402. For example, the timeframe identifier 408 can specify when the users 102 lived together, worked together, dated, and so forth.

The relationship identifier 402, the relationship type identifier 406, the relationship details identifier 406, and/or the timeframe identifier 408 may be selectable via a drop down menu, a text entry box, a check box, and/or via any other selection method or combination of selection methods. According to exemplary embodiments, the social editor inquiry 402 is pre-populated with selections when sent to the users 102 with whom confirmation of the relationship is sought. Further, the social editor page 400 can be automatically populated, partially or wholly, utilizing data already stored about the users 102 and/or the relationship the users 102 have established with one another on previous occasions.

The arrangement, presentation, display, and/or subject matter described in connection with FIGS. 3 and 4 may vary and still remain within the scope of various embodiments. For example, additional relationship questions may be utilized in association with the social relationship page 400 or additional types of the biographical data 304 may be displayed via the social network display page 300.

For example, the user A 102A can complete the social editor page 400 by selecting from the relationship identifier 402, the relationship type identifier 404, the relationship details identifier 406, the timeframe identifier 408, and/or any other identifiers that may be provided via the social editor page 400, in order to provide details about the relationship the user A 102A has with the user B 102B, for example. The user B 102B can then be sent the pre-populated social editor page 400 and asked to confirm the data provided by the user A 102A. The user B 102B can confirm the accuracy of the data on the social editor page 400, modify the data on the social editor page 400, add to the data on the social editor page 400, and/or deny the accuracy of the data on the social editor page 400.

The details about the relationship established via the social editor page 400 can be stored by the relationship storage module 206. For example, a relationship database (not shown) may be utilized to map the relationships between the users 102 associated with the social network engine 106. The map can show a network of the relationships between the users 102, in one instance.

The subject matter of the inquiries and the data associated with the social editor page 400 may include any topics, such as membership in a club, a team, a church, etc.; common courses, classes, institutions, programs of study, etc.; common travels, journeys, adventures, parties, conferences, etc.; common familial relationships, friends, acquaintances, romantic partners or interests, musical interests, restaurants, bars, pubs, etc.; whether two or more of the users 102 met randomly, accidentally, purposefully, via online activities, etc.; and/or whether two or more of the users 102 have never met, etc. Any type of data can be established via the social editor page 400, as discussed herein.

As discussed herein, a confirmation request can be sent to the users 102 in response to completion of the social editor page 400. The social relationship editor module 204 can send a communication, for example, to the user B 102B that the user A 102A selected the user B 102B as a person the user A 102A may know or with whom the user A 102A wishes to establish a relationship. The user B 102B can elect to confirm the data provided by the user A 102A, adjust or edit the data, send a message to the user A 102A regarding the relationship, deny the existence of the relationship, add data about the relationship, and so forth. If the user B 102B edits or adds to the data, the user A 102A may be asked to confirm the added or edited data, according to exemplary embodiments.

The users 102 can view the status of the relationships with other of the users 102 via a display page that indicates the status. For example, the social network display page 300 can include the status of the relationships with each of the users 102 displayed on the social network display page 300. The biographical data 304, for example, can also display whether the relationship with the user about which the biographical data 304 is displayed has accepted, denied, or is reviewing the data about the relationship or proposed relationship. The status may comprise a written description of the relationship, the time of the relationship, and/or any other details about the relationship.

Details of a social map generated based on the relationship the users 102 have with one another may also be displayed via the social network display page 300. For example, a social map that shows details about a relationship between the user B 102B and the user A 102A may be generated, displayed, and or accessed by the users 102.

The social network display page 300 can also display the users 102 in an ascending or descending order according to a chronology associated with the relationships the users 102 have with other users. For example, the user N 102N may be displayed before the user B 102B in a listing requested by the user A 102A because the user A 102A has known the user N 102N for a longer period of time than the user B 102B. The users 102 can be displayed according to common groups, association with common events, situations, or occurrences, and so forth.

Referring now to FIG. 5, a flow diagram of an exemplary process for social mapping is illustrated. At step 502, data about one or more social network members is received. The social network members may comprise the users 102 described herein, such as the user A 102A, the user B 102B, and/or the user N 102N. Any number of users may comprise the social network members. As discussed herein, the users 102 can utilize the social networking website associated with the social network engine 106 to access and/or provide data about other of the users 102.

At step 504, a first social network member is allowed to identify at least one second social network member to establish a relationship. For example, the user A 102A can select the user B 102B with whom the user A 102A wants to establish a relationship. The user A 102A can select the user B 102B from a list, such as the list displayed via the social network display page 300 discussed herein.

At step 506, the data is sent to the second social network member about the first social network member based on the identification. For example, once the user A 102A selects the user B 102B for establishing a relationship, the user A 102A may be directed to a social editor page 400 generated by the social relationship module 204. The social relationship editor module 204 can, optionally, pre-populate the social editor page 400 with data already stored by the relationship storage module 206 about the user A 102A and the relationship user A 102A may already have established or partially established with the user B 102B, for example.

At step 508, input is received from the second social network member in response to the data. For example, the user B 102B may confirm the data provided by the user A 102A utilizing the social editor page 400. The user B 102B may also deny that the data is accurate or deny the relationship generally, edit the data, add to the data, and so forth. Any action taken by the user B 102B in response to receiving the data regarding the relationship or proposed relationship from the user A 102A is within the scope of various embodiments.

At step 510, the relationship is confirmed based on the input in order to map the first social network member to the at least one second social network member. According to some embodiments, the social network engine 106 can determine whether or not to confirm the relationship before the relationship is confirmed. The social relationship editor module 204 can confirm the relationship, for example, based on the input from the user B 102B. The confirmation may comprise establishing that the relationship data is accurate, editing the relationship data, denying the relationship data, adding to the relationship data, and/or optionally requesting further confirmation from the user A 102A.

According to some embodiments, the relationship data is mapped to the user B 102B once the user B 102B confirms the relationship data as accurate. In other words, if the user B 102B confirms that the user B 102B, indeed, has a relationship of some type with the user A 102A, the relationship details can be added to a profile associated with the user B 102B, for example.

The user A 102A and/or the user B 102B may also be asked if privacy settings should be modified in response to the newly established relationship. For example, the user B 102B may confirm the relationship with the user A 102A, but may only want the user A 102A to have access to the data about the user B 102B that the user B 102B allows the users 102 within a specific community or group to access. The privacy settings can be modified at any time. For example, a privacy settings module (not shown) may be associated with the social network engine 106 for specifying the privacy settings for each of the users 102 with respect to which data about the users 102 each other of the users 102 can access.

According to other embodiments, the relationship data may be presented or displayed according to the relevance of the relationship data to online or offline interactions between the users 102, to timeframes based on online or offline interactions, and so forth. For example, the social network engine 106 can suggest other of the users 102 with whom the user A 102A may want to form a relationship based on the fact that those other users 102 attended the same school, at the same time.

Predictive tools for forecasting which of the users 102 will establish relationships, analytical tools for determining the nature and influence the users 102 have on one another, and any other tools may be developed based on the relationship data. For example, the social network engine 106 can identify stories about the user B 102B that the user A 102A will find most interesting based on the relationship data.

Further, the users 102 can be grouped according to the established relationships. The groupings can be utilized to display various types of information to the users 102, suggest other of the users 102 with which relationships should be established, and so forth.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the elements associated with the social network engine 106 may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments. 

What is claimed is:
 1. A method comprising: identifying an established relationship between a first member and a second member of a social network, the established relationship indicating the first member and second member are directly connected based on a mutually declared relationship between the first and second members on the social network; identifying a grouping of members defining a subset of members of the social network that includes the first member and the second member based on a common characteristic; selecting a third member for the first member to establish a mutually declared relationship with based on the identified grouping, the identified grouping also including the third member, the third member possessing the common characteristic, the third member not having an established relationship with the first member, and the third member not having an established relationship with the second member; providing, to the first member, a suggestion to establish a mutually declared relationship on the social network with the third member; receiving an indication from the first member that the first member would like to establish a mutually declared relationship with the third member; responsive to receiving the indication, providing, to the third member, the indication that the first member would like to establish a mutually declared relationship with the third member; receiving input from the third member to confirm the mutually declared relationship with the first member; and responsive to receiving the input, storing the mutually declared relationship in a relationship database, the relationship database mapping relationships between users within the social network.
 2. The method of claim 1, where one or more privacy settings are associated with the established relationship between the first member and the second member, the privacy settings being provided by one of the first member and the second member and governing who can access the details about the established relationship.
 3. The method of claim 1, where the established relationship between the first member and the second member is also established between one or more other members of the social network.
 4. The method of claim 1, wherein the established relationship between the first member and the second member includes details about the established relationship.
 5. The method of claim 4, wherein the details about the established relationship describes a time or timeframe associated with the established relationship.
 6. The method of claim 4, wherein the details about the established relationship between the first member and the second member are input by one of the first member and the second member and the details are verified by the other of the first member and the second member before the relationship between the first member and the second member is established.
 7. The method of claim 4, wherein the details about the established relationship between the first member and the second member describe how the first member and the second member know each other.
 8. The method of claim 7, wherein the details about the established relationship between the first member and the second member further comprise at least one of a group consisting of the first member and the second member having lived together, the first member and the second member having worked together, the first member and the second member having been classmates, the first member and the second member being related, and the first member and second member having dated.
 9. The method of claim 4, wherein the details about the established relationship between the first member and the second member include a status of the established relationship.
 10. The method of claim 9, wherein the status of the established relationship between the first member and the second member describes whether a member of the established relationship has approved the details in the established relationship, the status being one of: accepted the details, rejected the details, or reviewing the details.
 11. The method of claim 1, wherein the grouping comprises members belonging to a particular community within the social networking website.
 12. The method of claim 11, wherein the community is categorized according to at least one of school attended, workplace and geographical location.
 13. The method of claim 1, further comprising providing a suggestion to the first member to establish a relationship with another member, in addition to the third member, in the grouping shared by both the first member and second member of the social network.
 14. The method of claim 1, wherein the common characteristic is a self-declared social attribute on the members' profiles.
 15. The method of claim 1, wherein the third member is selected from the grouping based on a projected measure of influence of the third member to the first member.
 16. The method of claim 15, wherein the projected measure of influence of the third member to the first member is determined based on a relevance to the first member of social networking content posted by the third member accessible to the second member that is inaccessible to the first member based on access privileges for the social content.
 17. The method of claim 15, wherein the projected measure of influence of the third member to the first member is determined based on a projected measure of influence of the third member to the second member, and a projected measure of influence of the second member to the first member.
 18. The method of claim 1, further comprising receiving a modification to the details about the established relationship between the first member and the second member from one of the first member and the second member.
 19. A non-transitory, computer-readable medium comprising instructions that, when executed by a processor, cause the processor to: identify an established relationship between a first member and a second member of a social network, the established relationship indicating the first member and second member are directly connected based on a mutually declared relationship between the first and second members on the social network; identify a grouping of members defining a subset of members of the social network that includes the first member and the second member based on a common characteristic; select a third member for the first member to establish a mutually declared relationship with based on the identified grouping, the identified grouping also including the third member, the third member possessing the common characteristic, the third member not having an established relationship with the first member, and the third member not having an established relationship with the second member; provide, to the first member, a suggestion to establish a mutually declared relationship on the social network with the third member; receive an indication from the first member that the first member would like to establish a mutually declared relationship with the third member; responsive to receiving the indication, provide, to the third member, the indication that the first member would like to establish a mutually declared relationship with the third member; receive input from the third member to confirm the mutually declared relationship with the first member; and responsive to receiving the input, store the mutually declared relationship in a relationship database, the relationship database mapping relationships between users within the social network. 